doc: add macOS Arm runnable build notes#753
Conversation
Document a local macOS/Arm workflow for configuring, building selected host-side targets, staging a runnable app bundle, and applying the signing order and entitlement choices needed for developer testing. This is explicitly a local non-packaging workflow and leaves the Darwin installer and release signing paths unchanged. Signed-off-by: Roberto Nibali <rnibali@gmail.com>
|
Thank you for your pull request and welcome to our community! To contribute, please sign the Oracle Contributor Agreement (OCA).
To sign the OCA, please create an Oracle account and sign the OCA in Oracle's Contributor Agreement Application. When signing the OCA, please provide your GitHub username. After signing the OCA and getting an OCA approval from Oracle, this PR will be automatically updated. If you are an Oracle employee, please make sure that you are a member of the main Oracle GitHub organization, and your membership in this organization is public. |
Signed-off-by: Roberto Nibali <rnibali@gmail.com>
Signed-off-by: Roberto Nibali <rnibali@gmail.com>
9371375 to
0cc0945
Compare
|
Withdrawing this documentation PR until its prerequisites land. Re-running the documented commands showed that current main does not produce the claimed runnable GUI result: Homebrew Qt configuration needs #747, the generated environment needs #752, and VBoxDxMt needs the narrowed #748 build fix. The documentation should be recreated and tested end-to-end after those changes are available. |
Summary
Add
doc/technical/DarwinArmRunnableBuild.wikiwith a local macOS/Arm runnable-build workflow.The note covers:
VirtualBox.appcopy for local testing;Why
This workflow is currently easy to reconstruct incorrectly from configure output, kBuild variables and Darwin installer signing logic. A short technical note makes host-side macOS/Arm iteration more reproducible without changing packaging or release-signing behavior.
Validation
git diff --checkCloses #751.